Handle protocol agnostic URI with domain in canonical link #345
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…t to always add protocol and domain if protocol is missing
|
Thanks. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently Shariff expands canonical URI read from
og:urlor canonical link tag with protocol and domain, if it doesn't find a leading "http" in the URI.Example on domain test.com:
"
/index.html" expands to "http://test.com/index.html"This behavior produces invalid results if the URI has two leading slashes (a protocol agnostic URI with domain) as it expands "
//test.com/index.html" on domain test.com to "http://test.com//test.com/index.html"The pull request fixes this, as only the protocol will be added in such cases.